FSCSI DEBUG Messages

These Messages are logged only in debug mode (device/protocol driver trace turned on) and are used to help debug problems. Contact AIX SAN support.

Detail Data SENSE DATA


NOTE: Below is a portion of the AIX 5.3 and AIX 6.1 error templates. Click here to see full error template
AIX Version 5 and below

RRRR RRRR AAAA AAAA BBBB BBBB CCRR RRRR RRRR YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ GGGG GGGG OOOO OOOO OOOO OOOO EEEE EEEE
EEEE EEEE VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV
...


AIX Version 6 and above


hhhh hhhh AAAA AAAA BBBB BBBB CCtt vvvv TTTT YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ
GGGG GGGG pppp pppp OOOO OOOO OOOO OOOO EEEE EEEE EEEE EEEE ssss ssss ssss ssss
Error Code
AAAA AAAA
What it means What to do
0x0000 000d A iocl has been sent from a process and the node name has not been set by the calling process An AIX Kernel trace may help determine the calling process.
0x0000 0010 EINVAL returned from LUN reset command. Most likely indicates that the target LUN does not support a reset. The driver issued a target reset instead. Verify with the vendor whether the device should support LUN reset. If the device is a disk, check the value of the lun_reset_spt attribute. An AIX kernel trace may help determine the requesting process.
0x0000 0031 The adapter driver has reported that the link is down Check connection to the SAN
0x0000 0032 The adapter driver has reported that the link is up Check connection to the SAN
0x0000 0033 The adapter has reported that it has received a LOGO (logout) from a device. Check with the device vendor to find out why the device sent the logout.
0x0000 0034 The adapter has reported that it has received a PRLO (Process logout) from a device. Check with the device vendor to find out why the device sent the logout.
0x0000 0035 The adapter has reported that it has received a LIP (Loop Initialization Protocol) or an SCN (state change notification) for the SAN. Check the connection to the SAN. In a fabric environment , check if the fabric has become segmented.
0x0000 0037 The adapter has reported that it has receive a SCN (state change notification) from the SAN Check whether any storage ports have dropped off the SAN.
0x0000 0038 The adapter driver has reported that the link is down. Check the connection to the SAN.
0x0000 0039 Notification from the adapter driver that a Group or Domain State Change Notification was received Check the SAN Fabric to determine whether any target ports have dropped off or whether the SAN fabric has become segmented.
0x0000 003a Logged when target_info was found in the Group or Domain State Change SCN. Check the SAN to determine why this target dropped off the fabric.
0x0000 003b Logged when the adapter has been halted in preparation for a firmware download. Verify that a firmware update is taking place.
0x0000 003c Logged when the adapter has been resumed after being halted. Verify that a firmware download completed successfully.
0x0000 004c Logged when a Fabric Busy was reported by the adapter Check the SAN fabric for issues that might prevent remote ports from processing requests.
0x0000 00a6 Logged when a device head has requested a restart to this a device Target info is included
0x0000 00a7 Logged when a target reset has been issued Target info is included
0x0000 00a8 Logged when a lun reset has been issued Target info is included
0x0000 00a9 (prior to AIX 5.3 TL 5 Logged when request for system memory (xmalloc) has failed. Ensure sufficient memory is allocated to the system. Check for components using excessive kernel heap. Contact IBM software support.
0x0000 00a9 (AIX 5.3 TL5 or later) Logged when a protocol driver target_info structure is found to be damaged. Contact AIX support.
0x0000 00ba Logged when old and new scsi_id values after a dynamic tracking event are the same. Most likely a cable moved back to original place on fabric during a given dynamic tracking iteration. INFORMATIONAL
0x0000 00c2 Target info with a stale scsi_id was found following a GID_PN, GPN_ID, PLOGI, or move_login. INFORMATIONAL
0x0000 00c4 Logged when a heuristic match was made for a dev_info lookup during an ioctl call. This most likely indicates a stale target_info/dev_info for devices that could not be tracked following dynamic tracking events Ensure all target ports are logged into the SAN so that dynamic tracking can complete INFORMATIONAL
0x0000 00ca Logged when an ioctl thread has been awoken and either SCN was received or a name server query is needed Ensure the SAN fabric is stable so dynamic tracking operations can complete. INFORMATIONAL
0x0000 00ce Logged when target_info was found with a stale scsi_id INFORMATIONAL
0x0000 00dc Logged when head driver sent a SC_DEV_RESTART, but the scsi_id for the target is not stale INFORMATIONAL
0x0000 00e1 Logged When an ioctl was made with scsi_id and the scsi_id and target info has changed. INFORMATIONAL
Target_info included.
0x0000 00e5 Logged when scsi_id for a SCIOLSTART and scsi_id recorded with the adapter are the same and dynamic tracking is turned off. Resolve the application error or enable dynamic tracking.
0x0000 007a Logged when the adapter driver indicates that the adapter has been reset, This message is informational.only.
0x0000 007b The device driver has received a FC ARP from a device in the SAN. This message is informational only,
0x0000 00c2 In debug mode, the AIX target info had a scid_id that was not current following a move login, get ID, get PN or port login completion. . Something has changed in the SAN, this is a SAN configuration issue
INFORMATIONAL
0x0000 00c4 In debug mode,A heuristic match was made in a device info lookup. This was most likely due to a change in the SAN on a device that does not support dynamic tracking, This is a debug informational only message.
0x0000 00ca In debug mode, the program thread waiting on a dynamic operation has resumed. This is a debug informational only message .
0x0000 00ce In debug mode, AIX target info was found to be out of sync following a Get ID, Get port name or move login,
Something has changed in the SAN,
This is a debug informational only message.
If dynamic tracking is enabled, the new scsi_id should be determined automatically. If dynamic tracking is not enabled, the target will remain inaccessible until the scsi_id returns to its original value, (e.g. when the cable is moved to its original port), or until the devices on the target are unconfigured and reconfigured.
0x0000 00dc in debug mode, a restart device command was received for a target and the scis_id appears to be current.
Something has changed in the SAN,
This is a debug informational only message
0x0000 00e1 In debug mode, An request from AIX was made with a scsi_id and a lookup has of the target info indicates that the scsi_id has changed. This is a debug informational only message.
0x0000 00e5 In debug mode, The start command is starting a device with a SCSI id that is already started., the cmd is failed if dynamic tracking is turned off. This is a debug informational only message.



.

.
.